…or interfaces/types);

refactor: discriminator type schema parser (own file)
feat: improve discriminator type dev exp

fix: problem with dot in query params

fix: critical bugs based with extract types and enums
fix: sort types option (sort was not correctly work with nested or extracted types)
internal: change process with using custom templates
BREAKING_CHANGE: remove `rawModelTypes` from output api configuration

feat: ability to sort routes;

Signed-off-by: Sora Morimoto <[email protected]>

Signed-off-by: Sora Morimoto <[email protected]>

Signed-off-by: Sora Morimoto <[email protected]>

Update GitHub Actions workflow

Update vulnerable deps

`signal` key has defined its key as optional, not necessarily the value even though this happens implicitly. No key means no value which translates to `undefined`:
```ts
    signal?: AbortSignal | null;
```

To support exactOptionalPropertyTypes it would have to be defined as:
```ts
    signal?: AbortSignal | null | undefined;
```

While you could say the key isn't optional (removing ?), which then requires an explicit undefined value:
```ts
    signal: AbortSignal | null | undefined;
```
That would require an explicit undefined being passed.

Given this key is part of TS definitions and module augmentation is overkill, just "oring" from undefined to an expected value (in this case null) solves the problem.

Replacing: #457

fix: onCreateRoute skip behaviour

# Conflicts:
#	CHANGELOG.md
#	package-lock.json
#	src/schema-parser/schema-parser.js
#	src/schema-parser/schema-utils.js
#	src/schema-routes/schema-routes.js
#	src/util/name-resolver.js
#	tests/spec/extract-enums/test.js

fix: Use type-only import for axios types

Use type-only import for axios types

fix non-object custom spec extensions

fix: input instead of output in readme

Supporting exactOptionalPropertyTypes

Fix regex to match numbers in path parameters

BREAKING_CHANGE: enable discriminator mapping;
BREAKING_CHANGE: add eslint

Add more option for custom config [#503]